4.3. Repeating Entries
The following test cases verify that recurring events can be synchronized between device and server.
In particular
Repeating calendar events can be created
Repeating calendar events can be modified (exceptions added/removed)
Repeating calendar events can be deleted
Test ID | Objective | Procedure | Expected Result |
|---|---|---|---|
3.1 Create Daily Repeat (every day, bounded) | Verify that a daily repeat can be synchronized Five day conference | Create an appointment on 23rd April 2007 with a daily repeat until 27th April 2007 Perform a synchronization | Device calendar should display 5 occurrences of a daily repeating meeting Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.2 Create Daily Repeat (every other day, unbounded) | Verify that a daily repeat can be synchronized Meeting every other day | Create an appointment on 23rd April 2007 with a daily repeat every other day Perform a synchronization | Device calendar should display a daily repeating meeting every other day starting from 23rd April 2007 The repeat pattern should remain unbounded (in other words, it should repeat forever) Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Meeting should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.3 Create Daily Repeat (every 7 days, unbounded) | Verify that a daily repeat can be synchronized Weekly Staff Meeting | Create an appointment on 2nd May 2007 with a daily repeat every 7 days Perform a synchronization | Device calendar should display a weekly meeting every seven days (every Wednesday) from 2nd May 2007 The repeat pattern should be the same visible pattern as a weekly repeat and it should be unbounded Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.4 Create Weekly Repeat (every Wed, unbounded) | Verify that a weekly repeat can be synchronized Meeting every Wednesday | Create an appointment on 2nd May 2007 with a weekly repeat on Wednesday Perform a synchronization | Device calendar should display a weekly meeting every Wednesday from 2nd May 2007 The repeat pattern should remain unbounded Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.5 Create Weekly repeat (Wed & Fri, unbounded) | Verify that a weekly repeat can be synchronized Swimming class held every week on Wednesday and Fridays | Create an appointment on 2nd May 2007 with a weekly repeat on Wednesday and Friday Perform a synchronization | Device calendar should display a weekly meeting with occurrences on Wednesday and Fridays from 2nd May The first two occurrences should be 02/05/07 and 04/05/07 The repeat pattern should remain unbounded Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.6 Create Fortnightly Repeat (unbounded) | Verify that a weekly repeat can be synchronized Project status meeting held every two weeks | Create an appointment on 1st May 2007 with a fortnightly repeat Perform a synchronization | Device calendar should display an appointment every two weeks starting from 1st May The repeat pattern should remain unbounded Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.7 Create Monthly By Date Repeat (unbounded) | Verify that a monthly by date repeat can be synchronized Utility bill payment on 15th day of the month | Create an appointment on 15th May 2007 with a monthly by date repeat Perform a synchronization | Device calendar should display an appointment on 15th of every month starting from 15th May 2007 The repeat pattern should remain unbounded Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.8 Create Monthly By Day Repeat (first occurrence, bounded) | Verify that a monthly by date repeat can be synchronized Monthly meeting on the first Monday of every month | Create an appointment on 7th May 2007 repeating every month on the first Monday for a year (13 occurrences in total) Perform a synchronization | Device calendar should display an appointment on the following dates: 07/05/2007, Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.9 Create Monthly By Day Repeat (nth occurrences, bounded) | Verify that a monthly by day repeat can be synchronized Monthly meeting on the 2nd Tuesday of every month | Create an appointment 2nd & 3rd Sunday of every month starting on 13th May 2007 until 10th June 2007 (3 occurrences in total) Perform a synchronization | Device calendar should display an appointment on the following dates: 13/05/2007, Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.10 Create Monthly By Day Repeat (last occurrence, bounded) | Verify that a monthly by day repeat can be synchronized Monthly meeting on the last Friday of every month | Create an appointment on the last Friday of every month starting 25th May 2007 until 29th June 2007 (2 occurrences in total) Perform a synchronization | Device calendar should display an appointment on the following dates: 25/05/2007, Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.11 Create Yearly Repeat (every year, unbounded) | Verify that anniversary events can be synchronized Birthday St Patrick’s Day (17th March) | Create an anniversary entry for Valentine’s Day (14th February 2007) on server Perform a synchronization | Device calendar should display an anniversary event on 14/02/2007 and future years (2008, 2009 etc.) The repeat pattern should remain unbounded Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.12 Create Yearly Repeat (every year for 5 years, bounded) | Verify that yearly events can be synchronized | Create an event with a yearly repeat on 1st April 2007 for five years Perform a synchronization | Device calendar should display an event on the following dates: 01/04/2007, Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.13 Create Yearly Repeat (every 4 years, bounded) | Verify that yearly events can be synchronized Leap year occurs every four years on 29th February | Create an event with a yearly repeat on 29th February 2004 every four years until 01/03/2012 Perform a synchronization | Device calendar should display an event on the following dates 29/02/2004, Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.14 Create custom repeat ( | Verify that custom repeat can be synchronized Dates for a lecture series: Tuesday this week, Wednesday next week, & Friday the following week. | Create custom repeat pattern Tuesday 1st May 2007, Wednesday 9th May 2007, Friday 18th May 2007 Perform a synchronization | Device calendar should display the event on the following dates: 01/05/2007, Level 0 & 1 device: Individual occurrences will not be linked Level 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.15 Create repeat combination | Verify that combinations of repeat patterns can be synchronized Daylight Saving Time starts on second Sunday in March in 2007 | Create appointment with a repeat combination, for example: Second Sunday in March every year ( Perform a synchronization | Device calendar should display event on 2nd Sunday of March (11th March 2007) The repeat pattern should remain unbounded Level 0 & 1 device: Individual occurrences will not be linked Level 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.16 Create repeating event plus custom repeat ( | Verify that more complex repeat patterns can be synchronized Weekly meeting with an extra meeting this week | Create a weekly repeating meeting (every Monday starting 5th May 2007) and add an additional Perform a synchronization | Device calendar should display weekly repeat every Monday starting 5th May 2007 and an additional meeting occurrence on 7th May with the same event description Level 0 & 1 device: Individual occurrences will not be linked Level 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.17 Create a repeating event with exceptions ( | Verify repeating meetings with exceptions can be synchronized Daily repeating meeting except for Wednesday | Create a daily repeating meeting starting 30th April 2007 until Friday 4th May 2007. Create meeting exception on Wednesday 2nd May (i.e. cancel meeting) | Device calendar should display daily repeat between 30/04/07 and 04/05/07 with no meeting on 02/05/07 Level 0 & 1 device: Individual occurrences will not be linked Level 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.18 Create a custom repeat with exceptions ( | Verify that more complex repeat patterns can be synchronized | Create custom repeat pattern Perform a synchronization | Device calendar correctly displays repeating pattern Level 0 & 1 device: Individual occurrences will not be linked Level 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.19 Create repeating event plus custom repeat and exceptions ( | Verify that more complex repeat patterns can be synchronized | Create custom repeat pattern Perform a synchronization | Device calendar correctly displays repeating pattern Level 0 & 1 device: Individual occurrences will not be linked Level 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.20 Modify anniversary | Verify that modification of meeting details does not cause device representation to become non-repeating | Create anniversary event on 4th July 2007 on device Perform a synchronization Modify subject of event on server Perform a synchronization | Device calendar correctly displays anniversary event on 04/07/07 Server modification of event subject is correctly synchronized to client Level 0 device: Individual occurrences will not be linked Level 1 & 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.21 Modify occurrences of repeating meeting | Verify that modification of the repeat rule is correctly synchronized to the device | Create daily repeating meeting starting on 1st May 2007 until 5th May (5 occurrences) Perform a synchronization Cancel occurrence on 4th May & 5th May (select this and future instances when deleting) from server Perform a synchronization | Device calendar displays repeating meeting 1-5th May After synchronization, device calendar displays meeting 1-3rd May only Level 0 & 1 device: Individual occurrences will not be linked Level 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.22 Modify exceptions of repeating meeting | Verify that addition, modification and deletion of exceptions is correctly synchronized | Create daily repeating meeting starting on 1st May 2007 until 5th May (5 occurrences) Perform a synchronization Cancel occurrence on 4th May & 5th May (select this and future instances when deleting) from server Perform a synchronization Extend meeting to 4th May (Modify exception) Perform a synchronization | Device calendar displays repeating meeting 1-5th May After second synchronization, device calendar displays meeting 1-3rd May After third synchronization, calendar displays meeting 1-4th May Level 0 & 1 device: Individual occurrences will not be linked Level 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.23 Delete recurring meeting | Verify deletion of recurring meeting is correctly synchronized to the device | Create recurring meeting on server Perform a synchronization Delete recurring meeting from server Perform a synchronization | Device calendar displays recurring meeting After synchronization, device calendar no longer displays recurring meeting Level 0 & 1 device: Individual occurrences will not be linked Level 2 device: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.24 Create Daily Repeat (every day, bounded) | Verify that a daily repeat can be synchronized Five day conference | Create an appointment on 23rd April 2007 with a daily repeat until 27th April 2007 Perform a synchronization | Server calendar should display 5 occurrences of a daily repeating meeting Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.25 Create Daily Repeat (every other day, unbounded) | Verify that a daily repeat can be synchronized Meeting every other day | Create an appointment on 23rd April 2007 with a daily repeat every other day Perform a synchronization | Server calendar should display a daily repeating meeting every other day starting from 23rd April 2007 The repeat pattern should remain unbounded (in other words, it should repeat forever) Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.26 Create Daily Repeat (every 7 days, unbounded) | Verify that a daily repeat can be synchronized Weekly Staff Meeting | Create an appointment on 2nd May 2007 with a daily repeat every 7 days Perform a synchronization | Server calendar should display a weekly meeting every seven days (every Wednesday) from 2nd May 2007 The repeat pattern should be the same visible pattern as a weekly repeat and it should be unbounded Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.27 Create Weekly Repeat (every Wed, unbounded) | Verify that a weekly repeat can be synchronized Meeting every Wednesday | Create an appointment on 2nd May 2007 with a weekly repeat on Wednesday Perform a synchronization | Server calendar should display a weekly meeting every Wednesday from 2nd May 2007 The repeat pattern should remain unbounded Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.28 Create Weekly repeat (Wed & Fri, unbounded) | Verify that a weekly repeat can be synchronized Swimming class held every week on Wednesday and Fridays | Create an appointment on 2nd May 2007 with a weekly repeat on Wednesday and Friday Perform a synchronization | Server calendar should display a weekly meeting with occurrences on Wednesday and Fridays from 2nd May The first two occurrences should be 02/05/07 and 04/05/07 The repeat pattern should remain unbounded Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.29 Create Fortnightly Repeat (unbounded) | Verify that a weekly repeat can be synchronized Project status meeting held every two weeks | Create an appointment on 1st May 2007 with a fortnightly repeat Perform a synchronization | Server calendar should display an appointment every two weeks starting from 1st May The repeat pattern should remain unbounded Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.30 Create Monthly By Date Repeat (unbounded) | Verify that a monthly by date repeat can be synchronized Utility bill payment on 15th day of the month | Create an appointment on 15th May 2007 with a monthly by date repeat Perform a synchronization | Server calendar should display an appointment on 15th of every month starting from 15th May 2007 The repeat pattern should remain unbounded Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.31 Create Monthly By Day Repeat (first occurrence, bounded) | Verify that a monthly by date repeat can be synchronized Monthly meeting on the first Monday of every month | Create an appointment on 7th May 2007 repeating every month on the first Monday for a year (13 occurrences in total) Perform a synchronization | Server calendar should display an appointment on the following dates: 07/05/2007, Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.32 Create Monthly By Day Repeat (nth occurrences, bounded) | Verify that a monthly by day repeat can be synchronized Monthly meeting on the 2nd Tuesday of every month | Create an appointment 2nd & 3rd Sunday of every month starting on 13th May 2007 until 10th June 2007 (3 occurrences in total) Perform a synchronization | Server calendar should display an appointment on the following dates: 13/05/2007, Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.33 Create Monthly By Day Repeat (last occurrence, bounded) | Verify that a monthly by day repeat can be synchronized Monthly meeting on the last Friday of every month | Create an appointment on the last Friday of every month starting 25th May 2007 until 29th June 2007 (2 occurrences in total) Perform a synchronization | Server calendar should display an appointment on the following dates: 25/05/2007, Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.34 Create Yearly Repeat (every year, unbounded) | Verify that anniversary events can be synchronized Birthday St Patrick’s Day (17th March) | Create an anniversary entry for Valentine’s Day (14th February 2007) on server Perform a synchronization | Server calendar should display an anniversary event on 14/02/2007 and future years (2008, 2009 etc.) The repeat pattern should remain unbounded Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.35 Create Yearly Repeat (every year for 5 years, bounded) | Verify that yearly events can be synchronized | Create an event with a yearly repeat on 1st April 2007 for five years Perform a synchronization | Server calendar should display an event on the following dates: 01/04/2007, Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.36 Create Yearly Repeat (every 4 years, bounded) | Verify that yearly events can be synchronized Leap year occurs every four years on 29th February | Create an event with a yearly repeat on 29th February 2004 every four years until 01/03/2012 Perform a synchronization | Server calendar should display an event on the following dates: 29/02/2004, Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.37 Create custom repeat ( | Verify that custom repeat can be synchronized Dates for a lecture series: Tuesday this week, Wednesday next week, & Friday the following week. | Create custom repeat pattern Tuesday 1st May 2007, Wednesday 9th May 2007, Friday 18th May 2007 Perform a synchronization | Server calendar should display the event on the following dates: 01/05/2007, Level 0 & 1 server: Test cannot be performed Level 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.38 Create repeat combination _Optional test — Mobile UI may not allow creation of this type of repeat | Verify that combinations of repeat patterns can be synchronized Daylight Saving Time starts on second Sunday in March in 2007 | Create appointment with a repeat combination, for example: Second Sunday in March every year ( Perform a synchronization | Server calendar displays event on 2nd Sunday of March (11th March 2007) The repeat pattern should remain unbounded Level 0 & 1 server: Test cannot be performed Level 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.39 Create repeating event plus custom repeat ( | Verify that more complex repeat patterns can be synchronized Weekly meeting with an extra meeting this week | Create a weekly repeating meeting (every Monday starting 5th May 2007) and add an additional Perform a synchronization | Server calendar displays weekly repeat every Monday starting 5th May 2007 and an additional meeting occurrence on 7th May with the same event description Level 0 & 1 server: Test cannot be performed Level 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.40 Create a repeating event with exceptions ( | Verify repeating meetings with exceptions can be synchronized Daily repeating meeting except for Wednesday | Create a daily repeating meeting starting 30th April 2007 until Friday 4th May 2007. Create meeting exception on Wednesday 2nd May (i.e. cancel meeting) | Server calendar displays daily repeat between 30/04/07 and 04/05/07 with no meeting on 02/05/07 Level 0 & 1 server: Test cannot be performed Level 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.41 Create a custom repeat with exceptions ( | Verify that more complex repeat patterns can be synchronized | Create custom repeat pattern Perform a synchronization | Server calendar correctly displays repeating pattern Level 0 & 1 server: Test cannot be performed Level 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.42 Create repeating event plus custom repeat and exceptions ( | Verify that more complex repeat patterns can be synchronized | Create custom repeat pattern Perform a synchronization | Server calendar correctly displays repeating pattern Level 0 & 1 server: Test cannot be performed Level 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.43 Modify anniversary | Verify that modification of meeting details does not cause server representation to become non-repeating | Create anniversary event on 4th July 2007 on server Perform a synchronization Modify subject of event on device Perform a synchronization | Server calendar correctly displays anniversary event on 04/07/07 Device modification of event subject is correctly synchronized to server Level 0 server: Test cannot be performed Level 1 & 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.44 Modify occurrences of repeating meeting | Verify that modification of the repeat rule is correctly synchronized to the server | Create daily repeating meeting starting on 1st May 2007 until 5th May (5 occurrences) Perform a synchronization Cancel occurrence on 4th May & 5th May (select this and future instances when deleting) from device Perform a synchronization | Server calendar displays repeating meeting 1-5th May After synchronization, server calendar displays meeting 1-3rd May only Level 0 & 1 server: Test cannot be performed Level 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |
3.45 Delete recurring meeting | Verify deletion of recurring meeting is correctly synchronized to the server | Create recurring meeting on server Perform a synchronization Delete recurring meeting from device Perform a synchronization | Server calendar displays recurring meeting After synchronization, server calendar no longer displays recurring meeting Level 0 & 1 server: Test cannot be performed Level 2 server: Appointment should be shown as a single recurrence set (e.g. an icon may be shown to indicate the appointment is recurring)  |